chore(deps): update tunit to 1.5*#6171
Conversation
thomhurst
added
dependencies
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
Overview
This is a Renovate-generated dependency update PR that bumps all TUnit-related NuGet packages from 1.48.6 → 1.50.0, and tightens the floating version constraints in project templates from 1.* → 1.5*.
Analysis
Consistency ✅
All TUnit packages are updated together in a single PR: TUnit, TUnit.AspNetCore, TUnit.Core, TUnit.Engine, TUnit.Assertions, TUnit.Assertions.FSharp, and TUnit.Playwright. No partial updates.
Template Version Constraint Change — Worth a Second Look
The template files shift from 1.* to 1.5*. In NuGet's floating version syntax, 1.5* matches any version whose string representation starts with 1.5 (e.g. 1.50.0, 1.51.0), but not 1.60.0 or higher. This is intentional behavior by Renovate to keep templates from silently pulling in newer minor versions, but it does mean:
- Once TUnit reaches
1.60.x, new projects scaffolded from these templates will be pinned to an outdated range unless the templates are updated again. - If the project moves fast (which it has —
1.48→1.50in this cycle), this constraint will need regular maintenance.
This is a reasonable tradeoff (predictability vs. freshness), but it's worth being aware that the Renovate constraint-narrowing is now the mechanism keeping templates current. As long as Renovate PRs like this one are merged promptly, there's no issue.
No concerns with the Directory.Packages.props changes — pinning to a specific 1.50.0 version for internal test/sample project references is the right call.
Summary
Low-risk, routine version bump. The only thing worth noting is the implication of the 1.5* constraint in templates, which is a Renovate convention rather than a bug. Safe to merge.
Code ReviewOverviewThis is a Renovate-generated dependency update PR that bumps all TUnit-related NuGet packages from AnalysisConsistency ✅ Template Version Constraint Change — Worth a Second Look The template files shift from
This is a reasonable tradeoff (predictability vs. freshness), but it's worth being aware that the Renovate constraint-narrowing is now the mechanism keeping templates current. As long as Renovate PRs like this one are merged promptly, there's no issue. No concerns with the SummaryLow-risk, routine version bump. The only thing worth noting is the implication of the |
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
2 participants
This PR contains the following updates:
1.*→1.5*1.48.6→1.50.01.48.6→1.50.01.48.6→1.50.01.*→1.5*1.48.6→1.50.01.48.6→1.50.01.48.6→1.50.01.*→1.5*Release Notes
thomhurst/TUnit (TUnit)
v1.50.0: 1.50.0What's Changed
Other Changes
Full Changelog: v1.49.0...v1.50.0
v1.49.0: 1.49.0What's Changed
Other Changes
Dependencies
Full Changelog: v1.48.6...v1.49.0
v1.48.6: 1.48.6What's Changed
Other Changes
Dependencies
Full Changelog: v1.48.0...v1.48.6
v1.48.0: 1.48.0What's Changed
Other Changes
Dependencies
Full Changelog: v1.47.0...v1.48.0
v1.47.0: 1.47.0What's Changed
Other Changes
Dependencies
Full Changelog: v1.46.0...v1.47.0
v1.46.0: 1.46.0What's Changed
Other Changes
Dependencies
New Contributors
Full Changelog: v1.45.29...v1.46.0
v1.45.29: 1.45.29What's Changed
Other Changes
Dependencies
Full Changelog: v1.45.22...v1.45.29
v1.45.22: 1.45.22What's Changed
Other Changes
Dependencies
New Contributors
Full Changelog: v1.45.8...v1.45.22
v1.45.8: 1.45.8What's Changed
Other Changes
Dependencies
Full Changelog: v1.45.0...v1.45.8
v1.45.0: 1.45.0What's Changed
Other Changes
Dependencies
Full Changelog: v1.44.39...v1.45.0
v1.44.39: 1.44.39What's Changed
Other Changes
defaultliteral for value-type assertion parameters by @JohnVerheij in #5919Dependencies
Full Changelog: v1.44.0...v1.44.39
v1.44.0: 1.44.0What's Changed
Other Changes
/to partial endpoint paths (#5838) by @thomhurst in #5874Dependencies
Full Changelog: v1.43.41...v1.44.0
v1.43.41: 1.43.41What's Changed
Other Changes
Dependencies
Full Changelog: v1.43.38...v1.43.41
v1.43.38: 1.43.38What's Changed
Other Changes
Full Changelog: v1.43.37...v1.43.38
v1.43.37: 1.43.37What's Changed
Other Changes
Dependencies
Full Changelog: v1.43.11...v1.43.37
v1.43.11: 1.43.11What's Changed
Other Changes
Dependencies
New Contributors
Full Changelog: v1.43.2...v1.43.11
v1.43.2: 1.43.2What's Changed
Other Changes
Dependencies
Full Changelog: v1.41.0...v1.43.2
v1.41.0: 1.41.0TUnit Should() Assertions (beta)
This versions comes with a beta version of TUnit.Assertions.Should - meaning that you can do:
myCode.Should().BeEqualTo(fluentShouldSyntax);For more information see the docs: https://tunit.dev/docs/assertions/should-syntax
What's Changed
Other Changes
Dependencies
Full Changelog: v1.40.10...v1.41.0
v1.40.10: 1.40.10What's Changed
Other Changes
Dependencies
Full Changelog: v1.40.5...v1.40.10
v1.40.5: 1.40.5What's Changed
Other Changes
Dependencies
Full Changelog: v1.40.0...v1.40.5
v1.40.0: 1.40.0What's Changed
Other Changes
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate.